Open-PEOPLE : Ergonomics

Our software platform is composed of several tools implemented as a set of Eclipse plugins using the Eclipse RCP standard "extension point" mechanism. This is the lightweight software integration model we decided to use during the conception of the OPSWP (see deliverable D2.2 for details), whose graphical consistency is guaranteed a minima thanks to the basic UI mechanisms (SWT widgets, workspace, etc.) of the Eclipse RCP. Each one of the integrated software tools is part of the model-driven workflow used by our platform to implement its features; however, these tools are not basically conceived to work together, thus undermining the coherency and usability of the OPSWP. Since the usability of our future software platform is a major concern for us, we are putting much effort into the harmonization of the various software elements to offer the best possible user experience to the system architects who will be our main users. The purpose of this document is to describe how we intend to provide good ergonomics to the OPSWP: we will especially explain the choices we made about the GUI conception. Ergonomics are only a question of usability, which depends on the good organization of GUI, on good use of visual components, forms, and so on. Ergonomics don't define neither the graphic charter nor the visual identity of our software: these "artistic" considerations are part of the project's task 6 (dissemination). The present study is divided into several consecutive parts: we first begin by analyzing user profiles and their related tasks, then we review the technical and architectural constraints that are imposed to us. From all of these, we eventually build a style guide, that defines the usability requirements that shall be followed as guidelines to implement the graphical user interfaces (GUIs) of the OPSWP software elements with the expected consistency. This document - not planned at the beginning - is part of task 2 of the OP project. This task is under the responsibility of the INRIA NGE team, and its main goal is the specification, conception and implementation of the OPSWP

Functional Validation of AADL Models via Model Transformation to SystemC with ATL

6 pagesInternational audienceIn this paper, we put into action an ATL model transformation in order to automatically generate SystemC models from AADL models. The AADL models represent electronic systems to be embedded into FPGAs. Our contribution allows for an early analytical estimation of energetic needs and a rapid SystemC simulation before implementation. The transformation has been tested to simulate an existing video image processing system embedded into a Xilinx Virtex5 FPGA

Multi-paradigm modelling for cyber–physical systems: a descriptive framework

The complexity of cyber–physical systems (CPSS) is commonly addressed through complex workflows, involving models in a plethora of different formalisms, each with their own methods, techniques, and tools. Some workflow patterns, combined with particular types of formalisms and operations on models in these formalisms, are used successfully in engineering practice. To identify and reuse them, we refer to these combinations of workflow and formalism patterns as modelling paradigms. This paper proposes a unifying (Descriptive) Framework to describe these paradigms, as well as their combinations. This work is set in the context of Multi-Paradigm Modelling (MPM), which is based on the principle to model every part and aspect of a system explicitly, at the most appropriate level(s) of abstraction, using the most appropriate modelling formalism(s) and workflows. The purpose of the Descriptive Framework presented in this paper is to serve as a basis to reason about these formalisms, workflows, and their combinations. One crucial part of the framework is the ability to capture the structural essence of a paradigm through the concept of a paradigmatic structure. This is illustrated informally by means of two example paradigms commonly used in CPS: Discrete Event Dynamic Systems and Synchronous Data Flow. The presented framework also identifies the need to establish whether a paradigm candidate follows, or qualifies as, a (given) paradigm. To illustrate the ability of the framework to support combining paradigms, the paper shows examples of both workflow and formalism combinations. The presented framework is intended as a basis for characterisation and classification of paradigms, as a starting point for a rigorous formalisation of the framework (allowing formal analyses), and as a foundation for MPM tool development

Open-PEOPLE : Architecture and Implementation

Our software platform is designed, from the very beginning, to be extensible : not only is the library of available components (both hardware and software) for modeling open for extension with user-defined data; the set of features offered by the platform is also extensible, all of these features being provided by "plug-ins" (a.k.a. "add-ons", i.e. code modules) integrated into OPSWP. The purpose of this document is to describe the implementation of the Eclipse plugins developed by INRIA NGE within the development of the OPSWP, in collaboration with all project partners. More specifically, it describes in further details the functionalities cited in deliverable D2.1, at each plugin level. This document, not planned at the beginning, is part of task 2. The task's goal is the specification, conception and implementation of OPSWP, which is the main task of the INRIA NGE team

A Semi-Automated Approach for the Co-Refinement of Requirements and Architecture Models

Requirements and architecture specifications are strongly related as the second provides a solution to a problem stated by the first. This coupling is typically realized by traceability links and maintaining such links becomes extremely difficult as both requirements and architecture specifications frequently evolve, and in particular when the architecture is refined providing an increasing level of details. In such case, not only the traceability must evolve but the requirements must be refined as well. We present a novel semi-automated approach to evolve non-functional requirements and their traceability links following system's architecture refinement in the context of design space exploration and automated code generation. The approach has been prototyped for AADL models refined with the RAMSES tool and for model transformations implemented as Story Diagrams

A multi-wavelenth study of sharpless 185

The HIT region S 185 (nebulosity around -y Cas) has been observed with the DRAO synthesis telescope in continuum and line emission at 21 cm, and in continuum emission at 74 cm. Continuum emission is clearly detected for IC 63 and is barely above the detection limit for IC 59. The emission of both clouds is thermal. A small amount ( ≈0.15 and 0.65 M for IC 63 and IC 59 respectively) of atomic hydrogen is found to be associated with the nebulae at velocity (LSR) near 0 km s⁻¹. Infrared emission from the clouds is also detected from the IRAS survey. The infrared and radio luminosities of the clouds are consistent with heating an dionization being produced by the B0.51V exciting star Cas. However, comparison of the amount of atomic material with the dissociation properties of Cas requires an age less than the main sequence life time by orders of magnitude. As a result, production of the extended atomic gas in the clouds by dissociation appears to have already ceased. The geometry of the region is inferred from the assumption that the clouds are bounded to the ionizing radiation coming from Cas. Accordingly, the weak radio continuum emission of IC 59 may be explained by one of the following hypothesis. The cloud is either farther away from the exciting star than the observed projected distance, or the Lyman continuum radiation from the exciting star is shielded by the postulated Be star envelope. In the former case, the line joining the cloud and the star would make an angle of 51° with the line of sight. The star-to-cloud distance would be about 3 pc. The strong infrared and weak continuum emissions would be due to the long extent (≈ 0.8 pc) of the cloud in the radial direction from the star. For the latter hypothesis, the envelope is shielding about 60% of the stellar ionizing luminosity. IC 63 appears to be composed of two main components: a series of dense filaments on the side of the exciting star which have been compressed by the stellar winds or radiation pressure from the star, and a mixture of lower density dust and dissociated hydrogen mostly located farther away from the exciting star. It is suggested that the density increase on the edges facing the exciting star would have allowed molecules to form in these tiny regions. IC 59, being farther away from the star, would only exhibit the low density component. Atomic hydrogen is also detected at VLSR —34kms⁻¹ near the infrared source IRAS 00556+6048. The emission is very fragmented and exhibits a shell-like structure that appears to surround the infrared source. The source which is probably not associated with S 185 would be located at a kinematic distance of ≈1.8kpc and may be a candidate for a dissociating star object. Another source with flux density 114 mJy, is detected in the 21cm Bonn continuum galactic plane survey. Surprisingly, the source is not detected in the NRAO survey performed at the same wavelength with a similar telescope. Moreover, it is not detected by the DRAO continuum observations while a coincident large ridge of HI emission at VLSR ≈ —29 km s⁻¹ is observed.Science, Faculty ofPhysics and Astronomy, Department ofGraduat

A MARTE to AADL Mapping

International audienc